1. Support DLQ, TTL
2. Support vhost name (tenant/namespace) by '/' partition
3. Add the admin api

Master Issue: #832,#861,#862,#863

Motivation

The current version does not support dead letter queues and message ttl, as well as delayed messages, which are often used in rabbitmq and we need to implement.

Modifications

1.For dead letter queue.
The queue binding parameter determines whether it is DLQ and uses the queue's own cursor to check for active consumers.
When there is an active consumer, it means that we do not need to control, when the active consumer is closed we need to start a task to detect, when there is no message to register to the listening queue, when awakened, first check whether there is an active consumer, if not, we need to route the message to the DLQ.
2.For TTL.
For DLQ, messages are routed to DLQ only after they expire. If they are not expired, a task countdown is registered and the time is up for detection

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

Check the box below.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)